Super Annoying BUG!! - Page 2 - Guild Wars Forums

Aranox · Dec 06, 2006, 01:31 PM // 13:31

In my opinion, this is actually NOT a bug.
It's simply the code not taking your action into account.

Here's what happens: you try to cast a spell.
The game checks your range and determines you're too far away to cast that spell, so it triggers code to start moving toward your target until you're in range.
The code to move you towards your target is simply the same code that triggers when you click somewhere. Your character is taking the shortest route towards the location of your target. And if there is an obstacle in the way, it will go around.
Making the code check every possible location within range and then determine every possible route towards that location to pick the shortest one is practically impossible (your target would be just as dead as it is now because of cpu load).
What might be possible is that when movement is triggered by activating a spell, for the pathing code to take into account the range of that spell and determine for every obstacle between you and your target if you can get within that range to your target before pathing a way around it.
This is assuming there are no other factors involved in determining whether movement is needed to cast that spell (such as line of sight).
And this can be a very difficult thing to program depending on how nested or complex the pathing code is.

It would be an improvement, but not a bugfix.

Fungus Amongus · Dec 06, 2006, 06:36 PM // 18:36

It's easier for us to use a movement key than for them to add decision making to the pathing, that's for sure. I don't see it as a bug at all, just something we need to be aware of.

ForgeWhelp · Dec 06, 2006, 06:48 PM // 18:48

The game is simply trying to get your char 'within' range. It doesn't really care what that range is, so if it thinks that you might be using a touch spell it paths you to your target. It just happens that you are using a ranged spell, it still wants to use the same logic. So what happens when they change the cosde and at first you cast a range spell so it runs towards the cliff, but then you cast a touch spell, but now you have to run all the way around to do that where as if you'd simply pathed in direct route on the first spell the 2nd would have been easier.

Basically understand how the game works and play that way...

Tarkin · Dec 06, 2006, 06:53 PM // 18:53

This is a very old "bug", i just move close to my target before casting... but i agree, this is annoying... will be cool if game staff fix it... but remember and if you want touch your target and the ai get you to a wall close to cast a spell but away from a touch?

...
But that dont annoying me, what is annoying me, is... the RED ENGINE GORED ENGINE GORED ENGINE GORED ENGINE GOing elona AI dont dodge... if you choose a target in a city or area and attack or want to just run to it, if my player find a npc, noob, hench or heroe in the way he just stop and still stoped, if i still pressing the button to attack he still stoped... i need do make a manual dodge... this happens to henchs, to minions... if i can remember this dont happens in tyria or cantha... or this is a new bad feature from a update, because i see it only in elona and dont paly in cantha or tyria, afther start playing in elona... this is annoying me a lot!!!!!!!!!!!!!!!!!!!!

Sli Ander · Dec 06, 2006, 07:03 PM // 19:03

From the attitude you present in this thread, if they actually changed it you would be back in a week saying that the AI is bugged because it moved you in a direct line towards your ally despite the fact that you clearly wanted to take the other route.

I've run into this problem when interrupting wurms in Tombs, and when healing in certain areas too. Solution? I find a different place to stand while healing(usually on the stairs behind a necro), and I manually move my ranger as far forward as possible before telling him to attack. Its a lot less stressful in the end to simply take small steps to solve the problem yourself.

Kamatsu · Dec 06, 2006, 09:12 PM // 21:12

Seeing as this is not really a question (and because this issue has been addressed).. and just a rant/whine/whinge about a "bug" in the movement AI in PvP..

BTW, all bug reports go to: www.guildwars.com/support/
- choose your region and submit a ticket.

Thread closed.

Dec 06, 2006, 09:12 PM // 21:12	#26
Kamatsu Moderator Join Date: May 2005 Location: Australia	Seeing as this is not really a question (and because this issue has been addressed).. and just a rant/whine/whinge about a "bug" in the movement AI in PvP.. BTW, all bug reports go to: www.guildwars.com/support/ - choose your region and submit a ticket. Thread closed. __________________ Have a moderation related issue or just want to chat? Send me a PM

Dec 06, 2006, 01:31 PM // 13:31	#21
Aranox Ascalonian Squire Join Date: Nov 2006 Profession: W/N	In my opinion, this is actually NOT a bug. It's simply the code not taking your action into account. Here's what happens: you try to cast a spell. The game checks your range and determines you're too far away to cast that spell, so it triggers code to start moving toward your target until you're in range. The code to move you towards your target is simply the same code that triggers when you click somewhere. Your character is taking the shortest route towards the location of your target. And if there is an obstacle in the way, it will go around. Making the code check every possible location within range and then determine every possible route towards that location to pick the shortest one is practically impossible (your target would be just as dead as it is now because of cpu load). What might be possible is that when movement is triggered by activating a spell, for the pathing code to take into account the range of that spell and determine for every obstacle between you and your target if you can get within that range to your target before pathing a way around it. This is assuming there are no other factors involved in determining whether movement is needed to cast that spell (such as line of sight). And this can be a very difficult thing to program depending on how nested or complex the pathing code is. It would be an improvement, but not a bugfix.

Dec 06, 2006, 06:36 PM // 18:36	#22
Fungus Amongus Wilds Pathfinder Join Date: Jul 2005 Guild: Fifteen Over Fifty [Rare] \| [Rare] Alliance	It's easier for us to use a movement key than for them to add decision making to the pathing, that's for sure. I don't see it as a bug at all, just something we need to be aware of.

Dec 06, 2006, 06:48 PM // 18:48	#23
ForgeWhelp Krytan Explorer Join Date: Jul 2006 Guild: TGW Profession: N/Mo	The game is simply trying to get your char 'within' range. It doesn't really care what that range is, so if it thinks that you might be using a touch spell it paths you to your target. It just happens that you are using a ranged spell, it still wants to use the same logic. So what happens when they change the cosde and at first you cast a range spell so it runs towards the cliff, but then you cast a touch spell, but now you have to run all the way around to do that where as if you'd simply pathed in direct route on the first spell the 2nd would have been easier. Basically understand how the game works and play that way...

Dec 06, 2006, 06:53 PM // 18:53	#24
Tarkin Jungle Guide Join Date: Dec 2005 Profession: W/N	This is a very old "bug", i just move close to my target before casting... but i agree, this is annoying... will be cool if game staff fix it... but remember and if you want touch your target and the ai get you to a wall close to cast a spell but away from a touch? ... But that dont annoying me, what is annoying me, is... the RED ENGINE GORED ENGINE GORED ENGINE GORED ENGINE GOing elona AI dont dodge... if you choose a target in a city or area and attack or want to just run to it, if my player find a npc, noob, hench or heroe in the way he just stop and still stoped, if i still pressing the button to attack he still stoped... i need do make a manual dodge... this happens to henchs, to minions... if i can remember this dont happens in tyria or cantha... or this is a new bad feature from a update, because i see it only in elona and dont paly in cantha or tyria, afther start playing in elona... this is annoying me a lot!!!!!!!!!!!!!!!!!!!!

Dec 06, 2006, 07:03 PM // 19:03	#25
Sli Ander Wilds Pathfinder Join Date: Jul 2006 Location: Deep in Maguuma, by the Falls Guild: Liberators of Agony Profession: Mo/R	From the attitude you present in this thread, if they actually changed it you would be back in a week saying that the AI is bugged because it moved you in a direct line towards your ally despite the fact that you clearly wanted to take the other route. I've run into this problem when interrupting wurms in Tombs, and when healing in certain areas too. Solution? I find a different place to stand while healing(usually on the stairs behind a necro), and I manually move my ranger as far forward as possible before telling him to attack. Its a lot less stressful in the end to simply take small steps to solve the problem yourself.